What
Adds endpoints to manage tax rules on a tax rate:

• Create a tax rule: POST /admin/tax-rates/:id/rules
• Delete a tax rule: DELETE /admin/tax-rates/:id/rules/:rule_id
• Replace tax rules: POST /admin/tax-rates/:id -- with { rules: [...] } in body.

Noteworthy things I bumped into

Updating nested relationships
A TaxRate can have multiple TaxRules and in this PR we enable users to replace all TaxRules associated with a TaxRate in one operation. If working with the module directly this can be done with:

taxModuleService.update(rateId, { rules: [{ ... }] })

Internally in the update function the TaxModule first soft deletes any TaxRules that exist on the TaxRate and then creates new TaxRules for the passed rules (see test).

A challenge arises when doing this in a compensatable way in a workflow. To see this imagine the following:

1. updateTaxRatesWorkflow gets the current data for the tax rates to update. This includes the tax rates' rules.
2. updateTaxRatesWorkflow calls taxModuleService.update with new rules.
3. Internally, the tax module deletes the rules in 1. and creates new rules.
4. Imagine an error happens in a following step and the workflow has to compensate.
5. The workflow uses the data from 1. and calls upsert. The tax module may correctly update the previous tax rules so they are no longer soft deleted. However, upsert (at least not by default) doesn't delete the new rules that were created in 2.

As illustrated by 5. compensating the update is not pretty. To get around this I instead opted to let the workflow handle setting the rules for a rate that makes the compensation more straightforward to handle. See workflow here.

Using nested workflows
Initially, I wanted to use the setTaxRateRulesWorkflow within the updateTaxRatesWorkflow. And this worked great for the invoke phase. However, when I needed to compensate the update workflow (and hence also had to compensate the set rules workflow), I found that the workflow engine no longer had the set rules transaction in memory and therefore could not roll it back. (This is where I try to rollback, but the transaction id can't be found).

I therefore opted to copy the steps from the set tax rate rules workflow into the update tax rates workflow; however, once we figure out a good way to ensure we can compensate nested workflows we should move to the nested workflow instead.

This also made me realize that the current implementation of workflows that use refreshCartPromotions may create inconsistencies in case of failures (cc: @riqwan).